GH-49275: [Doc] Update docs to specify disclosure of AI on mailing list messages#49277
GH-49275: [Doc] Update docs to specify disclosure of AI on mailing list messages#49277thisisnic wants to merge 3 commits into
Conversation
|
|
|
@rok I had 2 options which seemed different levels of reasonable: I got two options that seem reasonable: A.
B.
What do you think? Could go with something else entirely. |
|
Option A seems beter for the explicitness. In a "no unattended" agents kinda way |
|
I suppose the thinking is that we cannot hope to communicate to unattended agents simply for our communication bandwidth not being scalable. |
Yeah, I think "just a few is fine" sounds reasonable with the current volume, but looking at the recent shenanigans with matplotlib, this feels like it could get out of control very easily. And it's not hard to say "I was working on this PR and the AI tool wanted me to check the following - can you clarify which of those approaches is best?" or something. |
AlenkaF
left a comment
There was a problem hiding this comment.
Looks great, thanks for this!
| .. seealso:: | ||
| More information and links for subscribing to the mailing lists `can be found here <https://arrow.apache.org/community/>`_. | ||
|
|
||
| .. note:: |
raulcd
left a comment
There was a problem hiding this comment.
This is great, thanks for adding links to the current resources
| * Avoid pinging maintainers to request reviews; most maintainers have | ||
| limited time, and we will review PRs as bandwidth allows. AI agents | ||
| should never tag or ping maintainers. |
There was a problem hiding this comment.
I don't mind the occasional ping from a human contributor but I strongly agree on the AI agents should never tag or ping maintainers. As this is part of the AI guidelines I am completely fine with the overall Avoid pinging maintainers to request reviews on that context.
Rationale for this change
Replying to AI on the mailing list is annoying
What changes are included in this PR?
Specify people should disclose
Are these changes tested?
Nah
Are there any user-facing changes?
Just docs